Fix high CPU usage of idle workers #136
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This uses
deadqueue
, a FIFO-queue implementation wrappingcrossbeam_queue::SegQueue
. It extends it with a future onpop
which uses a nice semaphore logic internally allowing us toawait
on it. This gives us exactly what we need to not naively unblock the async task and retry the queue manually on every loop cycle, as there was otherwise no future to wait for before. This led originally to unnecessary waking of the runtime even when there was nothing to do, wasting CPU resources. With the newawait
/ future on the queue we have a chance now to do something else in the async runtime and come back as soon as there is something to do again.Closes: #127
📋 Checklist
CHANGELOG.md